Skip to content

Conversation

brunnerh
Copy link
Member

(Looks like an artifact from $on.)

@vercel
Copy link

vercel bot commented Oct 21, 2024

@brunnerh is attempting to deploy a commit to the Svelte team on Vercel, but is not a member of this team. To resolve this issue, you can:

  • Make your repository public. Collaboration is free for open source and public repositories.
  • Add @brunnerh as a member. A Pro subscription is required to access Vercel's collaborative features.
    • If you're the owner of the team, click here and add @brunnerh as a member.
    • If you're the user who initiated this build request, click here to request access.
    • If you're already a member of the Svelte team, make sure that your Vercel account is connected to your GitHub account.

To read more about collaboration on Vercel, click here.

@benmccann
Copy link
Member

The docs live in https://github.com/sveltejs/svelte/tree/main/documentation and are synced into this repo. Probably best to fix them there

I believe at the moment that sveltejs/svelte#13699 is being used as the synced branch, but once that is merged it will switch to main

@brunnerh
Copy link
Member Author

I'll open a new PR against the other repository later then, unless someone else integrates this first.

@brunnerh brunnerh closed this Oct 21, 2024
@brunnerh brunnerh deleted the component-set-migration branch October 21, 2024 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants